-
Notifications
You must be signed in to change notification settings - Fork 376
Documentation fixes with some linting #219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Remove Travis button as it's no longer used.
README.md
Outdated
|
||
```bash | ||
$ aws lambda invoke --function-name rustTest \ | ||
--cli-binary-format raw-in-base64-out \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be worth calling out you need the aws v2 cli for this to work. Some are using that but as it's relatively new, many are not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It might be worth calling out you need the aws v2 cli for this to work. Some are using that but as it's relatively new, many are not.
Great call. Should I add the invokcation command for both versions? Or highlight the need for --cli-binary-format
with v2? I'm learning towards the latter as it's less verbose.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've went with the following but happy to change! 56a745f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, let’s prefer version two of the CLI. I’d be surprised if the audience for this crate aren’t also early adopters of the newer CLI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My apologies it was late when I made the above commit 56a745f. It should say most users are using v1
.
I think as it stands the README.md
does a good job of documenting the command for both v1 & v2. Is there any change you would like here @davidbarsky ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, yeah. No change then. Thanks for doing this!
[package] | ||
name = "lambda" | ||
version = "0.1.0" | ||
authors = ["David Barsky <[email protected]>"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might drop the "client" part of this. That's an implementation detail most users won't likely care or care to know about. Just calling this "AWS Lambda Rust runtime" might get the point across and be a little bit more inline with https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the feedback. I've addressed this in f3337db
This is a closer fit to the convention for runtimes across different languages.
Most users are still using v2 of the cli. Let's keep things simple for them.
Also expanded on comment Co-Authored-By: David Barsky <[email protected]>
lambda/src/lib.rs
Outdated
//! be placed on an asynchronous main function. However, asynchronous main | ||
//! functions are not legal valid Rust, which means that a crate like | ||
//! [Runtime](https://github.com/rustasync/runtime) must be used. A main function |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Sorry for the back and forth on this; I reviewed this before my coffee hit.)
Can we reword this to say something along the lines of "Tokio is required; we suggest using #[tokio::main]
"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries at all. I'll get back to this in about an hour once I've food.
Fire away with any requests :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I only noticed this docs issue now since I wrote that; the two big issues are:
runtime
is deprecated.- This crate has a hard Tokio dependency (for now). Cross-runtime support is too hard and has too many open design questions, and until Rusoto supports runtimes other than Tokio, I don't think its worth attempting to support other runtimes in this crate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not totally familiar with tokio
but I've attempted to clear this section up. Anything you would like changed? Sorry if I'm misunderstanding something!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One last comment; then I'll merge this in. Thanks!
@davidbarsky Could this PR be linked with the following issue please? #84 |
Yup! If you’re to add a resolves [issue number] to the description of this PR, it’ll link and close that issue. |
Hi @davidbarsky is there anything you would like changed? |
@darrenmeehan No, this looks great! Sorry for the delay and thanks for the fix! |
Awesome thank you for the quick feedback. Looking forward to contributing some more. |
Description of changes:
README.md
to work with existing code.README.md
are ignored fromgit
Some code changes. I can revert this to make this PR cleaner if deemed more appropriate.
By submitting this pull request